As presented in the talks and documentation I’ve seen so far, DocC works for public
and open
Swift symbols. But how about stuff for internal use?
We are developing a fairly complex mixed source SDK with several components, that would benefit greatly from direct integration of auxiliary content for diagrams and so on. But since many of these parts are for internal use only, they have module or below level visibility.
Is there a way to build an internal documentation target that includes this information with DocC, and — if so — how?
You are correct, DocC generates documentation for the public symbols in your framework or package. As you can imagine, that was the first priority, but your case certainly is interesting.
Could you please file a Feedback Assistant request with details about your project’s setup and what you’d like to be able to do? These types of enhancement requests, especially with how you'd like to see it work, are super helpful.
Thanks!